The vROps PostgreSQL DB must be able to generate audit records when security objects are accessed.

Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

The vROps PostgreSQL DB must be able to generate audit records when security objects are accessed.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-239813	VROM-PG-000470	SV-239813r879863_rule		Medium

Description
Changes to the security configuration must be tracked. This requirement applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via specialized security functionality. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE

STIG	Date
VMW vRealize Operations Manager 6.x PostgreSQL Security Technical Implementation Guide	2023-09-12

Details

Check Text ( C-43046r663814_chk )
At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix Text (F-43005r663815_fix)
At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET log_statement TO 'all';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"